Draft
Conversation
Not final UI, focusing on functionality over form at this point
…nto feature/inertia-dashboard
brianjhanson
commented
Oct 31, 2025
Contributor
Author
There was a problem hiding this comment.
I'm a bit tempted to replace this with TanStack Query but I'm also a bit wary of hitching ourselves to that bandwagon.
Contributor
There was a problem hiding this comment.
I've found that in general axios/fetch requests are barely necessary when using Inertia as intended and for the few cases where they're needed fetch is enough.
As soon as there's something that's clicked or interacted with by the user for the action you either create a link (even if it's a POST or DELETE) or a form.
Especially since it makes it possible to do partial reloads
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When I started this, I thought, "I'll do the dashboard, that's not too complicated.". Guess what world? I was wrong. Turns out there's a lot of functionality packed into our little dashboard.
Even though this PR isn't finished, I wanted to open it to start getting feedback on the direction things are heading.
The general plan is to use Inertia with Vue to handle the rendering of the CP. The Vue pages will then render our web components from the
@craftcms/cppackage (#18010). General layout will be handled by Tailwind utility classes.All these together will hopefully help usher in a new era free from the quantum entanglement we find ourselves in with the current CSS.
Even though this PR is large already, there's still a good list of things that need to be tackled before we'll reach feature parity with the current Dashboard.
To-Do
settingsJsmay need to be evaluated when creating a widgetSlidePickercomponents